Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

Installing the DataDirect SQL ODBC drivers and the DataDirect ODBC branded drivers

If you are installing OpenEdge in a Windows operating system, you must have the following Microsoft Installers for this installation:

You must have the MDAC 2.6 Installer from Microsoft to install Microsoft Data Access Components (MDAC) in Windows operating systems. The OpenEdge Installation Utility contains the MDAC 2.6 Installer, which it automatically launches during installation. The MDAC 2.6 Installer is located at installation-path\%DLC%\odbc\install\mdac_typ.exe. You can find more information about the MDAC at Microsoft’s Web site at the following URL: http://www.microsoft.com/data/prodinfo.htm.
You must have the DCOM98 Installer from Microsoft to install the Distributed Component Object Model (DCOM). The OpenEdge Installation Utility installer contains the DCOM98 Installer, which it automatically launches during installation. The DCOM98 Installer is located at installation-path\%DLC%\odbc\install\dcom98.exe. You can find more information about DCOM98 at Microsoft’s Web site at the following URL: http://www.microsoft.com/Com/DCOM/Dcom98/redis.asp.

You must reboot your system after installing either the MDAC or the DCOM98 Installer.

DataDirect SQL ODBC drivers

The Installation Utility installs the DataDirect SQL ODBC driver files to the installation-path\bin directory. The Installation Utility also installs the files to %windir%\system32 for Windows operating systems. Table 1–9 lists the SQL driver files installed for the OpenEdge database.

Table 1–9: Driver files — Windows operating systems for SQL 

Database	Driver files
OpenEdge SQL	pgodbc.lic pgpro1019.dll pgpro1019R.dll pgpro1019S.dll procli92.dll (OpenEdge driver File)

Installing the DataDirect branded ODBC drivers

The Installation Utility installs the DataDirect branded ODBC driver files to the installation-path\bin directory. Table 1–10 lists the DataDirect branded ODBC driver files installed with the OpenEdge® DataServer for ODBC. You can refer to the odbcref.pdf file installed in the installation-path\bin directory for information on how to configure datasources to connect to the different databases that OpenEdge supports.

Table 1–10: Driver files — Windows operating systems with OpenEdge DataServer for ODBC  

Database	Driver files
All ODBC data sources	P1BAS20.dll P1BAS20R.dll P1UT120.dll P1UT120R.dll IVP1.LIC P1ICU21.dll
DB2 Common Server	P1DB221.dll P1DB221r.dll
Microsoft SQL Server 2000 and later	P1MSSS21.dll P1MSSS21r.dll
Sybase	P1ASE21.dll P1ASE21r.dll

Additional DataServer information for ODBC-related components

To use DataServer for ODBC, note the following points, Progress Software Corporation recommends that you use DataDirect Version 5.1. Also, you need the specific data-source software components and version numbers installed for the specific data sources you are using. Table 1–11 presents these software requirements.

Table 1–11: Data-source components and version numbers 

If you are using the DataServer for ODBC product from this data source. . .	Then you must install. . .
DB2	One of the following software requirements: DB2/MVS Version 3.1, 4.1, or 5.1. (These versions can include DDCS Multi-user Gateway Version 2.3 or later.) Also, DB2/MVS Versions 3.1 and 4.1 require IBM Client Access Enabler Version 2.11 or later. DB2/NT Version 5.0 or 6.1. (Either version can also include DB/2 Connect Version 5 or later.) DB2/6000 Version 5.0 or 6.1 (Either version can also include DB/2 Connect Version 5 or later.) DB2/400 Version .5 operating system (Version 5.3).
DB2/400	DB2/400 Version 5.3.
Sybase	Sybase adaptive Server System 10 or System 11 for data-source server software and Open Client Library Version 11.1.